Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 014 / pk232.arc / PK232COM.DOC < prev next >

Wrap

Text File | 1987-08-08 | 121KB | 2,641 lines

PK232COM VERSION 1.41 PAGE 1 PK232COM Version 1.41 (c) 1987 by G3ZCZ (C) Copyright 1987 - All Rights Reserved By Joe Kasser G3ZCZ POB 3419, Silver Spring, Md., 20901, USA. PK232COM is written and supported by Joe Kasser, G3ZCZ. The program is distributed as a Shareware product. You may freely copy and share the product with your friends, associates and other radio hams. If you decide to use the product, you are asked to become a registered user by sending a QSL card and a contribution to the author (suggested amount of $35.00 or equivalent in foreign currency. The contribution covers the cost of distribution of the updated disk, and supports the continual development of "Software for Amateur Radio". Upon receipt of your contribution, you will receive one free update disk), mail (electronic and regular) support, and notice of further releases. The update disk will contain any new versions of the software on this disk plus any new software, accompanying the series of articles currently being written on the applications of data processing concepts of microcomputers to amateur radio. Under no circumstances may this product be sold or distributed with another product without the express written permission of Joe Kasser, G3ZCZ. Joe Kasser, G3ZCZ will only support unmodified copies of this software. Your comments and suggestions for changes are however welcome. If you are the first to suggest a change that is implemented, you will be sent a complimentary copy of the disk with the change incorporated. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 2 CONTENTS ------------- 1.0 INTRODUCTION 1.1 PROGRAM HIGHLIGHTS 1.1.1 MORSE/BAUDOT/AMTOR/ASCII 1.1.2 PACKET RADIO 2.0 CRT DISPLAY 2.1 Status Display 2.2 Incoming Text Display 2.3 Outgoing Text Display 2.4 Command/Status Display. 3.0 Function keys. 3.1 Function Keys 3.1.1 Capture to Disk Toggle 3.1.2 Transmit a file 3.1.3 CAllsign Sequence. 3.1.4 Brag tape 3.1.5 Call CQ 3.1.6 Change Communications Modes 3.1.7 Call/Connect 3.1.8 Disconnect or Receive 3.1.9 Command Mode 3.1.10 Transmit Mode 3.2 Alt Function keys 3.2.1 Exit or return to DOS. 3.2.2 Initialize the PK-232. 3.2.3 Connect Status 3.2.4 Set Terminal Mode 3.2.4.1 SOLO 3.2.4.2 TRAFFIC 3.2.4.3 CQ/BEACON 3.2.4.4 READ THE MAIL 3.2.4.5 FEC 3.2.4.6 ALISTEN 3.2.4.7 ACHG 3.2.4.8 ARQ 3.2.4.9 Force LETTERS Case 3.2.4.10 Manual Mode 3.2.5 Monitor Channel Activity 3.2.6 Change Packet Connect / Contest / CQ text Message 3.2.6.1 Change Packet Connect Message 3.2.6.2 Change Contest Message 3.2.6.3 Change CQ text Message 3.2.7 Enter Call Sign 3.2.8 Not used. 3.2.9 Activate Transmit Buffer 3.2.10 Help PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 3 3.3 Shift Function Keys 3.3.1 Dir 3.3.2 Rename 3.3.3 List of Outgoing Messages 3.3.4 Delete 3.3.5 List of messages that have been sent. 3.3.6 Mail Beacon Activate 3.3.7 Retry a call/connect request 3.3.8 Not used. 3.3.9 Connected Indicator Reset. 3.3.10 OVER function. 3.4 Control Function Keys 3.4.1 Day Flag 3.4.2 CWID 3.4.3 Message Uploading 3.4.3.1 Leaving a Note in your system. 3.4.3.2 Leaving a message on an other PK232COM system [QSP]. 3.4.3.3 Uploading messages to another PK232COM system. 3.4.4 Show last few log entries. 3.4.5 Automatic CQ Sender 3.4.6 SELCAL 3.4.7 Beacon Activate Toggle/CQ Wait Delay Adjust. 3.4.7.1 Beacon Mode Toggle/On-Off 3.4.7.2 CQ Delay Time Adjust 3.4.8 Not used. 3.4.9 Transmit Buffer Clear 3.4.10 Log QSO 3.5 Shift/Baudrate Control keys 3.5.1 The RIGHT ARROW Key (Increase Baudrate). 3.5.2 The LEFT ARROW Key (Decrease Baudrate). 3.5.3 The UP ARROW Key (Change shift). 3.5.4 The DELETE Key (toggle USOS). 3.6 Additional keys 3.6.1 The HOME Key. 3.6.2 The DOWN ARROW key. 3.6.3 The Alt D key (display inhibit). 3.6.4 The Alt P key (printer toggle). 3.6.5 The Alt F key (Digipeat monitor toggle). 3.6.6 The Alt R key (Message Relay toggle). 4.0 PK232COM disk files 4.1 PK232COM.COM 4.2 PK232COM.RUN 4.3 PK232COM.SYS 4.3.1 The first line (callsign). 4.3.2 The second line (AMTOR SELCAL). 4.3.3 The third line (CQ Text). 4.3.4 The fourth and fifth lines (Band and Power). 4.3.5 The sixth line (CQ Delay time). 4.3.6 The seventh line (Message Relay Capability). PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 4 4.3.7 The eight line (Communications Port). 4.3.8 The ninth line (TNC type) 4.3.9 The remaining lines. 4.4 PK232COM.LOG 4.5 PK232COM.DIR 4.6 CONFIG.SYS 4.7 *.MBX 5.0 Initialization 6.0 Running the Program 7.0 Mailbox features (AMTOR/Packet Modes Only) 7.1 Answering Machine. 7.2 Mail Beacon (Annunciator). 7.3 How to leave a message 7.4 Remote File Downloading (Packet Mode Only). 7.5 Remote Beacon shutdown. APPENDIX 0. UPDATES/REVISION HISTORY APPENDIX 1. BUGS APPENDIX 2. MESSAGES IN A LOCAL AREA NETWORK APPENDIX 3 BASIC NC/L DICTIONARY APPENDIX 4. USING OTHER TNC'S. 4.1 TNC2 (MFJ 1274) APPENDIX 5. NOTES PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 5 1.0 INTRODUCTION PK232COM is a terminal interface program for the PK-232. It is designed only for the PK-232 built by Advanced Electronics Applications Inc. and not for just any TNC. Most of the packet radio features however should work on any TNC. It is designed to allow anyone to use and get the most out of the PK-232 for Morse, ASCII, BAUDOT, AMTOR and Packet Radio communications without having to keep the PK-232 manual handy. PK232COM is a sophisticated program. In its basic state it allows you to use the PK232 in an optimal manner. It configures the PK232 for you to maximise the communiations efficiency in the communications mode of your choice. That means for example, when working Packet on HF you need to program the PK232 parameters to different values than you would use on VHF to make maximum use of the mode (one significant difference is the length of the packet itself, for the longer it is, the greater the probability of QRM destroying it). This program will adjust the packet parameters for you. Since the computer is now involved, other features have been added to simplify operation, and several features have been automated. All these operations are performed using function keys as documented below. It will take a while to learn how to use this program in a manner that suits you, read this document and have fun, after all, isn't that one of the purposes of Amateur Radio. This documentation file is not a manual. It is a preliminary document. It is written to remind you of what the program can do. If there is enough interest (registrations) I will expand it. It is not designed to explain the theory behind the different communications modes. Read the PK232 Manual for more information. This program is designed to optimize the configuration of the PK232 in each communications mode and to provide some smart terminal features. 1.1 PROGRAM HIGHLIGHTS 1.1.1 MORSE/BAUDOT/AMTOR/ASCII Automatic CQ caller. Will call CQ repetitively and signal you when a reply is received. SELCAL. Automatic capture to disk of all ingoing and outgoing text of any QSO. 1.1.2 PACKET RADIO Automatic disk recording of all packet radio connects. Automatic indication of Packet connects. Local Area Network message store and forward. Digipeat monitoring and capture. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 6 AMTOR/PACKET Automatic Answering Machine capability with display of message queue. Automatic Beacon Mode CQ caller in Packet and AMTOR communications modes. Will call CQ repetitively and either work the connect and keep going after disconnect or signal you when a reply is received. Automatic logbook entries for Packet and Beacon mode AMTOR Connects, semi automatic logbook entries for other modes. Log file is compatible to that of the CONTEST program in the CONTEST.ARC archive and can be processed by the DBASE Logbook Package of PC-HAM by G3ZCZ for indexed listings, tracking of DXCC and other AWARDS, etc. Contest operation, sends standard mesage and automatically increments QSO count. Automatic optimized configuration of the TNC for each communications mode. Morse, ASCII, BAUDOT communication modes are HALF DUPLEX. One station is transmitting at any time. You thus have to use the Transmit/Converse and Receive/Disconnect function keys to turn the transmitter on and off respectively. AMTOR is also HALF DUPLEX but has some of the attributes of full duplex. In this mode you control who is talking through software, only one station can send data at a time, but you can type characters in to the buffer and they will be transmitted automatically when the other station turns the QSO over to you. Once you have linked with someone, you do not use the Receive/Disconnect function UNTIL THE QSO IS OVER. Both stations are communicating automatically thanks to the TNC. If you want the other operator to respond type the +? key sequence (or use shift function key 10). Packet Radio communications on the other hand is a full duplex mode of communications. Once you have connected with someone, you do not use the Receive/Disconnect function UNTIL THE QSO IS OVER. Both stations are communicating automatically thanks to the TNC. If you want the other operator to respond type the > key followed by the 'Enter' key (or use shift function key 10). Note that Morse, AMTOR, ASCII and BAUDOT are character mode communications in that each character you type is sent as you type them. In Packet Communications, the TNC stores them up and sends out a burst or packet when you type the 'Enter' key or you type enough characters to fill up a packet. Therefore don't forget to use the 'Enter' frequently, especially before you stop to think about what to send next. Any Terminal Node Controller (TNC) is a complex piece of equipment. It can operate in a Command Mode, in which you tell PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 7 it to do something, or in a Converse Mode in which you are using it to talk to other stations. Many people confuse the two when first getting on Packet. If you monitor the channels you will recognize command mode TNC instructions on the air, and when you use the TNC you will receive the "?What" reply when you type something thinking that you are in the Converse Mode but are really in the Command Mode. PK232COM is designed to make Packet operation simple using high level (Function key) commands. Version 1.0 has the following functions built in to it in a menu driven format. Morse Code 20 wpm (CW). BAUDOT with default of 45 WPM narrow shift (LSB). You may use the left and right arrow keys to change the baud rate (see below). ASCII 110 BAUDS narrow shift (LSB). Packet VHF or HF baud rates and shifts (LSB). AMTOR 100 BAUDS narrow shift (LSB). All communications operate in the 7 bit or normal ASCII mode. You cannot send 8 bit files (compiled programs, etc.) using Version 1.XX of PK232COM. Access to the PK-232 Command mode is provided in case the user wishes to override any of these defaults EXCEPT the 7 bit communications mode. IF YOU USE THIS PROGRAM, YOU STILL MUST READ THE PK-232 MANUAL. Note that AMTOR and PACKET are full duplex modes of communications. When you connect with someone, there is no need to use the transmit and receive function keys. In fact you will have problems if you do. Do not disconnect until the QSO is over. WARNING .... THIS PROGRAM OPERATES IN AN OPEN LOOP MODE. IT REMEMBERS WHAT INSTRUCTIONS OR COMMANDS IT GAVE THE TNC. IF FOR SOME REASON, THE TNC IS NOT SYNCHRONIZED TO THE PROGRAM YOU WILL NOT GET CORRECT DISPLAYS ON THE SCREEN. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 8 2.0 CRT DISPLAY The CRT display contains four areas as follows. ------------------------------------------------- | STATUS DISPLAY | ------------------------------------------------- | | | | | INCOMING TEXT DISPLAY | | | | | | | ------------------------------------------------- | OUTGOING TEXT DISPLAY | | ____________________________ | | |____________________________| | | | ------------------------------------------------- 2.1 Status Display A one line display at the top of the screen showing the status of the communications system. The left side of the screen normally displays the "capture to disk" or logging status, the center of the screen displays status information depending on which of the operational modes is active. 2.2 Incoming Text Display The center section of the screen displays data coming back from the PK-232. This consists of data received via the radio communications link, PK-232 status information and transmitted data echoed back by the PK-232. 2.3 Outgoing Text Display The lower area of the screen shows data being sent to the PK-232. This consists of command data from the program to the PK-232, text typed by the user and files being transmitted. 2.4 Command/Status Display. This screen located above the Outgoing Text Display shows the command dialog between the program (PK232COM) and the PK232. It is displayed for educational use so that you can see how the PK232 is being programmed. 3.0 Function keys. The operation of each of the function keys are explained below. 3.1 Function Keys 3.1.1 Capture to Disk Toggle This key toggles the "capture to disk" function. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 9 When the function is active, all incoming text (including 'Echo as sent' outgoing text) is stored on a disk (floppy or hard) in a file called 'PK232COM.RUN'. If this file does not exist the first time that the function is activated, it is created. From that time on, successive activations append new data to the contents of the file. Each time the function is activated a datestamp will be written to the file. When a Packet station connects the 'capture to disk' function will be activated automatically even if you have not set it active. Packet connects will thus be recorded in their entirety automatically unless you turn the logging off during the course of the QSO. The function will be deactivated at disconnect time unless you have toggled it on. You may later edit the file at your convenience with your favorite word processor. The function will automatically self terminate and close the log capture file if you forget to deactivate the function before terminating the program and returning to DOS. 3.1.2 Transmit a file This function allows you to transmit an ASCII file via the PK-232. You may abort the transmission sequence at any time by depressing any of the function keys, the keys on or associated with the numerical pad or the ESC key. While the file is being sent, you will see various things on your screens. The text of the file will be seen in the Input window as it is being sent to the TNC. During the file transfer, the status window will show the different states of the transmission. It begins with a signal that the message is being sent. If the text is long and fills the TNC buffer, you will see a message 'QRX PK232 BUFFER FULL' possibly followed by 'PK232 NOT RESPONDING'. This latter message will seem to blink periodically. When the PK232 signals that it is ready to accept more text, the message sequence will resume. When the file has been loaded into the PK-232 the computer will add the ^Z character to the outgoing text to signal to the recipient that the file PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 10 transmission is over. You may abort the file transmission sequence by depressing any function key,the 'ESC' key or any other Control or Alter- nate key on the keyboard. The computer will signal you (using the bell character, when the file has been loaded into the PK-232. Note that is not the same as the time that the PK-232 has transmitted the file, because the PK-232 incorporates a character buffer. 3.1.3 Call Sign Sequence. This function lets you transmit the following sequence <other call) DE <your call>. For example if you are 4X6AA and you are working G3ZCZ then this function would transmit the sequence G3ZCZ de 4X6AA. You use this at the start of a transmission in any mode except Packet. 3.1.4 Brag tape This function allows you to transmit a standard text file historically known as a "Brag Tape" via the PK-232. The brag tape file must be called PK232COM.TXT, and should be created with a word processor in the non-document mode. A sample file is included on this disk. Transmission of the Brag Tape may aborted in a similar manner to that of a regular file (see above). 3.1.5 Call CQ You use this function key to call CQ. In the Packet Communications mode, the PK-232 will transmit a line of text along with the CQ packet. The line of text is set up in the PK232COM.DAT file described in section 4. In the AMTOR communications mode, your SELCAL will be transmitted along with the CQ call in the FEC mode. 3.1.6 Change Communications Modes This function allows you to change the communications mode of the PK-232. Allowable modes are Morse code, BAUDOT, AMTOR standby, AMTOR Alisten, ASCII Packet and Signal. In the Packet mode you can choose VHF or HF operation in a single step by entering the letters V or H as well as the letter P for packet which will take you to a second prompt requesting VHF or HF. When you select the AMTOR standby mode you are placed into the 'standby receive' mode. If you want to read the mail on an existing AMTOR QSO in progress, select the AMTOR Alisten or chirpcopy mode. If you are in one mode, you will not be PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 11 able to see signals of another mode. Use the 'G' option to select the 'SIGNAL' mode. Read the PK232 documentation carefully to understand how this mode works. Once the PK232 has identified the digital signal it is tuned to, use the same function key a second time to select the relevant mode and set the baud rates and shift to display the data. 3.1.7 Call/Connect You use this function to call a station heard on the band, or to attempt a connect with another packet station. You may also use it to call 'QRZ' or even 'TEST'. In AMTOR the call will be sent in the ARQ mode to the SELCAL of the desired station. In the Packet Communications mode you can create a directory file and keep a list of names and callsigns. The computer will look up a name and call the station by its callsign. For example if you put Joe G3ZCZ as a line in the file, when you tell the computer to connect to Joe, it will try to connect to G3ZCZ. See section 4.5 which describes the PK232COM.DIR file for further information. In the Packet communications mode, if you want to loop back through someone else enter the '/' character followed by the call of the station you want to loop back through. For example if I (G3ZCZ) want to loop back through 4X6AA, I just need to enter /4X6AA as the call to connect to and the computer will tell the TNC to try to connect to G3ZCZ via 4X6AA. 3.1.8 Disconnect or Receive This function key returns the station to the receive communications (PK232 command) mode. It may also be used to abort the automatic CQ sequence. If you use it to abort a CQ sequence while the transmission is in progress, flush the PK232 transmit buffer using Control function key 9. 3.1.9 Command Mode This function puts the PK-232 into the command mode. At this time, the program is transparent and acts as a dumb terminal (except for placing incoming and outgoing text in the relevant windows). you use this mode for overriding any of the PK-232 default conditions. (SEE I TOLD YOU PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 12 THAT YOU HAD TO READ THE PK-232 MANUAL). 3.1.10 Transmit Mode This function places the PK-232 into the transmit or converse mode. The transmitter is turned on and the contents of the transmit buffer is transmitted. In the non packet communications modes, the outgoing characters will be echoed back from the PK-232 and displayed in the INCOMING window on the CRT as they are transmitted on the air. 3.2 Alt Function keys 3.2.1 Exit or return to DOS. Exits the program and returns you to DOS. When you exit the program, the TNC is put into the VHF default mode in which it rejects calls from any other stations. (Read about the 'CFROM' command in the TNC manual). you can thus if you wish leave it powered, and if you also leave the VHF radio powered up, you will be active as a digipeater, but at the same time anyone trying to connect with you will receive a busy signal. The MBX function (Reading the Mail) is also cleared at this time. 3.2.2 Initialize the PK-232. Sets up the defaults for the PK-232 from the file PK232COM.SYS. You should normally only have to run this function when you first power up the PK232 or change the batteries. 3.2.3 Connect Status When you are in the Packet communications mode, this function lets you see the state of the connection in the Command Window. It will show you if there are any unacknowledged packets en route to the other station. If you have been sending text, it is advisable to use this function before you disconnect, just to ensure that all the data has been received and acknowledged by the other party. You may use this function in either the TNC Command or the TNC Converse mode, but note that using this function will set the TNC to the Command Mode. 3.2.4 Set Terminal Mode This key allows you to set the terminal configuration mode. In the PACKET Communications mode, the function works in the following manner. After setting the terminal configuration mode, it returns you to the TNC command mode. In Packet communications many stations can use the channel PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 13 at the same time. Refer to the "MONITOR' and 'MBX' commands in the PK232 manual. You can set four Packet terminal modes as follows. 3.2.4.1 SOLO In this mode, you will only see messages addressed to you. You will only get messages from people who connect to you. (This corresponds to 'MONITOR 0'). 3.2.4.2 TRAFFIC In this mode you will see most of the traffic on channel. you can use this mode to check that the TNC is working. (This corresponds to 'MONITOR 4'). 3.2.4.3 CQ/BEACON In This mode, you will see CQ and BEACON packets on the channel. (This corresponds to 'MONITOR 1'). 3.2.4.4 READ THE MAIL Some packet channels are busy. To cut down on the number of messages sent on the channel, you can read the mail on a BBS or other station and get bulletins without connecting to that station yourself. You use this mode to do so. you will be prompted for the call whose packets you wish to monitor. Remember to enter the call of the station sending the packets, not the call of the one receiving them. (This corresponds to 'MONITOR 0' and 'MBX' callsign). You can also use this function to monitor both sides (read the mail) on a QSO on a busy packet channel. You may want to turn the Digipeat Data Display mode off when reading the mail. The Packet Terminal mode of operation will be shown in the Status window at the top of the screen. If you are reading the mail on a station, the callsign of that station will be shown next to the word "MAIL". If you are connected to someone, the call (and path) will be shown prefixed by the "*>" sequence. You also use this function to go into and out of the multiple connect mode. The default condition is one connect at a time. Should you opt for the PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 14 multiple connect mode, make sure you know what you are doing, and have set the CHSWITCH character. I recommend using the '\' (backslash) but if you do use it, don't transmit raw directory files in the mailbox file mode or you will see an error message. You don't have to be in the command mode to use the CHSWITCH character. Read all about CHSWITCH in the TNC manual. When you are in the multiple connect mode, an asterisk will be shown in the status window next to the word 'PACKET'. In the AMTOR communications mode you can also do four things as follows; 3.2.4.5 FEC Places the terminal into the FEC transmit mode. This puts you on the air, anything you type will be transmitted. 3.2.4.6 ALISTEN Read the Mail on a QSO. Unfortunately, when you tune in a chirpy AMTOR QSO in the ARQ or standby mode you won't get any copy on the QSO in progress. You can however read the mail on one by entering the ALISTEN mode. If you want to see a FEC CQ call you will have to return to the ARQ mode. 3.2.4.7 ACHG Force a changeover or 'break in'. If for any reason you want to interrupt the other station you send a 'BREAK' signal in software this way. 3.2.4.8 ARQ Return to the ARQ standby mode. You must be in this mode to receive signals from another station who is calling you. You may do it this way or via the main Mode Menu. When you tune for CQ calls, they sound somewhat like fast RTTY with a ringing sound similar to the connect alarm (but at a faster ringing rate) used by PK232COM. 3.2.4.9 Force LETTERS Case This function lets you force the receiver to the letters case if for some reason you appear to be in the numbers case. It will return you to the converse mode. 3.2.4.10 Override ROBOT Beacon This function lets you override the ROBOT BEACON and chat to a station that has PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 15 linked to the ROBOT. Use it after the message in PK232COM.TXT has been sent, ie when the other station is sending a message to you. 3.2.5 Monitor Channel Activity This function lets you see what calls the PK232 has heard recently on the Packet channels. You can see up to 18, with the data and time they were last logged by the PK232. If they were heard directly an asterisk (*) will be listed next to the call sign. If they were heard being re transmitted via another station, the asterisk (*) will not be shown. Refer to the 'MH' command in the PK232 manual. 3.2.6 Change Packet Connect/Contest Message 3.2.6.1 Change Packet Connect Message This function allows you to change the message that will be received by another packet station when it connects to you. Refer to the 'CTEXT' command in the PK232 manual. 3.2.6.2 Change Contest Message This function first toggles the contest mode. If the contest mode is active, the word 'TEST' and the number of the next QSO will be displayed in the status window. When the contest mode is toggles on, this function then allows you to set the starting QSO number and enter in the non changing or standard message that will be transmitted as part of an exchange of messages during a contest. The contest function is toggled off the next time you select this function, or when you change the PK232 Communications mode (ie. switch from Morse to BAUDOT). Note that while this does give you some semi automatic contest operation by using function keys, there is no checking of callsigns for duplicates built into the program. In a contest, you enter the callsigns and call the other station in the normal manner, then use this function key to transmit the exchange. In Morse, and RTTY don't forget to use function key 10 to turn on the transmiter first. 3.2.6.3 Change CQ text Message This function allows you to change the contents of the CQ text message string. This PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 16 is the string that is transmitted along with the CQ call. The default value is loaded from the PK232COM.SYS file. 3.2.7 Enter Call Sign This key lets you enter the call of any station calling you into the program. If you type the enter key in response to the prompt, you can later use the F3 (function key 3) to transmit the sequence "de <yourcall>". In AMTOR, you use it to enter the callsign of the station you want to or have called by means of the SELCAL. 3.2.8 Not used. You don't want to disconnect accidentally if you just depress function key 8 without the 'Alt' key. 3.2.9 Activate Transmit Buffer The use of this key sets PK232COM to the "Type Ahead" mode. Any characters then typed at the keyboard will be placed into the PK-232 transmit buffer. The contents of the buffer will be trans- mitted over the air when the transmit function is invoked [FK10]. THIS FUNCTION IS NOT ACTIVE IN THE PACKET MODE since Packet is a full duplex mode of communications. This feature allows you to 'type-ahead' as you can enter text into the transmit buffer while viewing incoming words in the INPUT window in the screen. Any characters typed from the keyboard will be echoed in the OUTGOING window on the screen. 3.2.10 Help The use of this key will activate the HELP menu in a special window on the screen. This window will remain on display until a character is typed at the keyboard, or a character is received by the computer from the PK-232. 3.3 Shift Function Keys 3.3.1 Dir This function shows you the directory of the logged in (active) disk drive. 3.3.2 Rename This function allows you to rename a file. You could for example rename a document file to a "callsign.OUT" file so that someone will receive it automatically next time they connect. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 17 3.3.3 List of Outgoing Messages This function shows you the outgoing messages that have not been sent. In other words, all files with the file extension of '.OUT'.See below for a description of outgoing messages in your "Packet Radio Answering Machine". 3.3.4 Delete This function allows you to delete a file 3.3.5 List of messages that have been sent. This function shows you the messages that have been sent. In other words, all files with the file extension of '.OLD'. 3.3.6 Mail Beacon Activate Using this function will also load a 'Mail :' list into your Packet communications mode Beacon and initiate a beacon transmission every 30 minutes (Refer to the BTEXT command in the TNC manual). If no mail is pending then beacon transmissions are inhibited. This conforms to good operating practice on crowded Packet channels. 3.3.7 Retry This function allows you to retry a connect that for some reason did not go through the first time. It save wear and tear on your fingers particularly if the desired connect path is via a number of relays. 3.3.8 Not used. You don't want to disconnect accidentally if you just depress function key 8 without the 'Shift' key. 3.3.9 Connected Indicator Reset. You use this function key to reset the PACKET and AMTOR beacon mode "connect has taken place indicator". This is a flashing [C] display in the status window. Whenever someone else connects to you this display will be activated. It is reset by this function key. If you are monitoring Packet traffic on a channel, you may not notice that a connect has previously taken place. This indicator alerts you to check the contents of the PK232COM.RUN disk file for any incoming messages. The number shown with the 'C' is the number of connects that have taken place since the Indicator was last reset. 3.3.10 OVER function. In the Packet communications mode this function sends your callsign followed by the > and Line feed characters. You may use this to signal PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 18 'OVER' in a packet contact. In the AMTOR communications mode this function sends a callsign sequence followed by the '+?' sequence of characters which are the software 'OVER' signal. In the MORSE and RTTY (Baudot and ASCII) communications modes, this function lets you transmit the following sequence <other call) DE <your call> and returns you to the PK232 Command Mode. For example if you are 4X6AA and you are working G3ZCZ then this function would transmit the sequence G3ZCZ de 4X6AA. You use this at the start of a transmission in any mode except Packet. If you have typed something into the 'type ahead buffer' then touch this function, the contents of the buffer first will be transmitted and that will then be followed by the callsign sequence. 3.4 Control Function Keys 3.4.1 Day Flag This function key puts the TNC into the command mode and loads the date into it from the computer. You use this to reset the TNC clock if it isn't that stabel, or to flag a date and time into the log file when in the non Packet modes. For example if you want to time tag a qso. 3.4.2 CWID This function key is used to send a CW identification when operating BAUDOT, ASCII or AMTOR. You use this if your license requires you to identify in morse code as well as in the operating mode. In AMTOR, the CWID is sent in the FEC mode. The identification consists of the sequence 'DE <your callsign>' where your call sign is that entered into the PK232 as 'MYCALL'. 3.4.3 Message Upload PK232COM contains store and forward routines for messages in a Local Area Network (LAN) as described in Appendix 2. Use this function to upload a message to another system compatable with PK232COM. 3.4.3.1 Leaving a Note in your system. In all modes you can leave a brief note (message) for another station. When you invoke this function the header is writ- PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 19 ten to the message file, then as you enter the text it is stored on the disk in the usual format. WHILE WRITING YOUR NOTE, ALL OTHER FUN- CTIONS OF PK232COM ARE INHIBITED OR LOCKED OUT. THUS IF SOMEONE CONNECTS TO YOU, THE TNC WILL KNOW THT BUT PK232COM WILL NOT. BE WARNED !!! When you invoke this function in the Packet mode While connected to another station. When you invoke this function, the computer will ask you to enter if you want to QSP or QRU. 3.4.3.2 Leaving a message on an other PK232COM system [QSP]. The QSP function lets you enter the callsign of the station you wish to leave a message for. It will then send the text sequence :QSP: <callsign>. The other station will either reply :QNO: followed by a number or :QRV: <cal- lsign>. The 'QNO' message means that the other computer cannot accept the message, the :QRV: message means that it is waiting for you to send it. If you get the :QRV: reply, go ahead and type the message, or send the text file containing the message. If you type the message, use a control Z (^Z) character and carriage return to terminate the message. You will then receive either a :QSL: frm the other station meaning that the message is accepted, or a :QNO: followed by a number which means that something went wrong and the message was not stored. 3.4.3.3 Uploading messages to another PK232COM system. The QRU function allows you to upload a number of messages to the other station. You use it when you have messages pending on your system and want to pass them to a third computer for storage in the network, while you take your com- puter off-line. You can only use this function with a station designated as a store and for- ward mail box, for which you have set up a <callsign>.MBX file (see section 7). This function may be triggered by you PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 20 using this control key or by the connecting station sending you a :QRU: command. When the sequence is over, the computer receiving the messages will transmit the command word :QJG: to signal that the sequence is complete. Should you receive it before you get any messages, then there weren't any pending. If you want to download messages from another PK232COM system connect to it and transmit the sequence :QRU: followed by at least one space character. That system will then respond to you as if the operator there had initiated a QRU function. Appendix 2 contains more information on the LAN capabilities of PK232COM. 3.4.4 Show last few log entries. This function displays the log entries made during the active session. If no QSO's have been made since the program was invoked the display window will be blank. Up to 5 log entries will be displayed in the window. You use this function for a quick look at which stations have connected to you in your absence. 3.4.5 Automatic CQ Sender This function will send a CQ sequence, wait about a minute or so and then repeat the CQ sequence every minute or so until it receives your call back from someone else. When it does so, it will alert you with a Connect Alarm signal and reset to the normal or listening mode. When the Automatic CQ sequence is in operation, an indication will be shown in the status window. The display will be constant while the transmitter is sending the CQ test, and will blink while the receiver is listening for a reply. The automatic CQ function will only work in the non Packet modes if the 'EAS' mode is set to 'ON' per the PK232COM.SYS file. In other words, you must be able to see the CQ text pop up in the outgoing window and then slowly echo in the incoming window for the function to work. The reason for this is that the "K K K" sequence is used to arm the software to look for your callsign. If it wasn't, the program would recognize your call being echoed to the screen and PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 21 think that someone had called you. In AMTOR you will get the connect alarm only when the replying station transmits the '+?' character combination. The check for the detection of your callsign and the connect alarm sequence only occur after a line feed character have been received. Under most conditions in AMTOR, many in RTTY, and some in MORSE, PK232COM will recognize the callsign of the station answering your CQ and display it in the status window. In the event that it fails completely, the sequence '--X--' will show up in the status window. Since the recognition algorithm use just look for the first word following the 'DE ' sequence and assumes that it has the callsign, be careful to check it when operating under QRM conditions. You can override the automatic call selection with the Enter Call- sign function key. The automatic CQ sequence is cancelled when an incoming call is detected, you push the disconnect function key, or if you change communications modes. 3.4.6 SELCAL This function key toggles the SELCAL feature on and off. When the SELCAL is activated, as shown in the status window, the incoming text from the PK232 is scanned. When either the letters "ZCZC" or 'your callsign' (as entered in the PK232COM.SYS file), the disk recording is turned on. All subsequent text will be stored in the PK232COM.RUN disk file until the letters "NNNN" are received. At that time the disk recording is turned off. You may use this feature when monitoring commercial RTTY broadcasts to record news and other information, or when calling CQ to start recording all incoming text and keep the QSO on disk. You may use the loggletoggle function to override the automatic turnoff if you wish. 3.4.7 Beacon Toggle On/Off/CQ delay time set. This function toggles the beacon option for the automatic CQ caller in the AMTOR and Packet communications modes. When active and CQ is being called, a [B] will be displayed in the status window. In this mode, the Automatic CQ sequence will resume after the AMTOR link is dropped or a PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 22 Packet Communications mode disconnect. In the beacon mode, the last few logbook entries will be displayed in the logpage window which overlays the outgoing text window at the bottom of the screen. In the Packet mode, the CTEXT message is the only transmission from you that the other station will receive, so make it good. In the AMTOR mode, the contents of the PK232COM.TXT file will be transmitted to the station who called you. The disk capture will then be turned on to record one transmission from that station. The QSO will then be logged to the logbook file. Don't forget to check the entries in case the computer made a mistake in recognizing the call sign of the other station. THIS MODE IS DESIGNED TO ENCOURAGE PEOPLE TO QSY OFF THE CROWDED PACKET HF CHANNELS. DO NOT USE IT ON A CROWDED HF CHANNEL OR ON AN ACTIVE VHF CHANNEL. IF YOU DO, YOU WILL SOON FIND THAT OTHER STATIONS HAVE SET THEIR TNC'S TO REJECT YOUR PACKETS, YOU WILL NOT WORK ANYBODY, YOU WILL JUST BA A SOURCE OF QRM AND WILL BE KNOWN AS SUCH. THE MODE IS ALSO DESIGNED FOR ROBOT BEACONS FOR THE HIGHER FREQUENCIES. FOR EXAMPLE IF YOU LEAVE IT RUNNING ON 10 METERS YOU NEVER KNOW WHEN A SHORT OPENING WILL ALLOW A QSO TO SOME PART OF THE WORLD. A DX CONTACT YOU WOULD HAVE MISSED OTHER- WISE. DO NOT LEAVE IT RUNNING ON 20 METERS WHEN THE BAND IS OPEN. YOU WILL JUST BE CAUSING QRM. FURTHER APPLICATIONS ARE IN METEORSCATTER AND OTHER "EXOTIC" MODES OF COMMUNICATIONS. If you are using this mode in a special event station or DX-pedition you may type characters into the transmit buffer, while the other station is sending to you. When he, she or even it turns it back to you, you will transmit those characters before the sign off sequence. 3.4.7.1 Beacon Mode Toggle/On-Off This function allows you to toggle the Beacon mode on and off. 3.4.7.2 CQ Delay Time Adjust This function allows you to change the time that the program waits for a response after a CQ call until the following one is transmitted. The default value is loaded from the PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 23 PK232COM.SYS file. You may want to experiment since the actual time will depend on the clock frequency of the computer. Make it a small number such as 4 or 6 when operating AMTOR or a DX- pedition, and make it a larger number such as 30 when operating on crowded packet channels. 3.4.8 Not used. You don't want to disconnect accidentally if you just depress function key 8 without the 'Shift' key. 3.4.9 Transmit Buffer Clear This function is used if the PK232 continues to transmit the characters you put into the 'type ahead buffer' after you have tried to shut it down. 3.4.10 Logbook. PK232COM allows automatic logbook entries for Packet and AMTOR Beacon mode Connects, and semi automatic logbook entries for other modes. The Log file is compatible to that of the CONTEST program in the CONTEST.ARC archive and can be processed by the DBASE Logbook Package of PC-HAM by G3ZCZ for indexed listings, tracking of DXCC and other AWARDS, etc. This is ideal for special event stations and DX-peditions, for the whole QSL process and further statistical analyses of their operation has been automated. For this function to work, the file PK232COM.LOG must be present on the disk. If it isn't there it will be created for you. After one logging operation has occurred, edit out the initial text. You must perform this editing operation before appending the contents of the logbook file to the logbook database of the PC-HAM LOGBOOK Package. Edit the log before appending it to the DBASE package, as there may be some null characters at the end of the file which may be recognised as a blank entry by DBASE It is also advisable not to let the each of the files get too big. When an AMTOR beacon mode or packet connect occurs, the connect is automatically logged. The connect path is placed in the comments section of the logbook entry. In the non packet modes, the log data entry is set up for you with default 599 values for the reports exchanged. You invoke this function to enter the data into the log. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 24 When you invoke the function you will be presented with the following typical menu in the menu window. LOG ENTRY DATE TIME CALL BND TX RX MODE POWER S R COMMENTS 87/04/27 17:28 20 599 RTTY 10 - - Date,tIme,Call,Bnd,Tx,Rx,Mde,Pwr,qSl snt,cOmmnts or Logit (*) ? You should reply with the capitalized character associated with each item. For example, if you want to change the Band, enter the letter 'b', to change the cOments, enter the letter 'o'. Touch the 'ENTER' key after you have made your choice and enter the text when prompted. You will then be presented with an updated entry. To enter the data into the logbook, use the 'l' key, to save the data but not make a log entry use the '*' character. You would do that if you want to change the band or power information. You may use the 'qSl sent' entry to tag the fact that you have written out a QSL card. The band and power information are set up from the default values stored in the configuration file PK232COM.SYS. They are displayed in the status window. If you are using the logging function, you should change them when changing bands/powers and quit the logging function with the '*' character so that you don't put a blank entry into the logbook. Note that you can also use this function to enter the odd SSB contact into the logbook file. If you do, use the characters 'SSB' or 'FM' for those voice modes to remain compatible with the rest of the DBASE logbook package. NOTE Do not use the comma character ',' in the comments field. If you examine the log entry you will see that all items are separated by comma's. If you use a comma character in the comments you will screw up the transfer of data into the logbook package. The comments field in the logbook is restricted to a maximum of 10 characters. If you try and enter more than 10, the surplus will be ignored. When you examine the DBASE logbook file, if it looks funny or the data are in the wrong, place, then you probably have the wrong number of comma PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 25 characters in some line. Delete the .DBF file and re-edit the .LOG file, to make sure that there are the correct number of comma characters. You will recognise the pattern readily enough. 3.5 Shift/Baudrate Control keys The following keys are used to control the Shift (Wide or narrow) and the baudrate in the BAUDOT, ASCII and PACKET communications modes. 3.5.1 RIGHT ARROW speeds up the baud rate. 3.5.2 LEFT ARROW slows down the baud rate. 3.5.3 UP ARROW toggles the shift from Wide to Narrow and back. 3.5.4 DELETE toggles the USOS function. In the PACKET mode the baudrate may be changed between 300, 600, 1200 and 2400 bauds. In the other modes all baud rates supported by the PK232 may be selected. The state of each of the above functions are displayed in the status window at the top of the screen. If USOS is active, 'USOS' will be shown. The shift is shown as 'W' or 'N' for wide or narrow respectively. 3.6 Additional keys 3.6.1 The HOME Key The home key will clear the window screen that the cursor happens to be in at the time that the key was depressed, and will then position the cursor at the top left hand corner of that window. 3.6.2 The DOWN ARROW key The DOWN ARROW key toggles the Normal Reverse Sideband function in all communications modes except MORSE. The sideband is depicted in the status window by the up and down arrows. If the down arrow is showing, you are set for Lower Sideband (LSB) which is the normally used one. If you have reversed the sidebands the up arrow be be shown in a flashing state. If you set your transceiver to LSB you will be set correctly for all modes. For CW operation you may set your rig to the CW position and ignore the sideband setting. 3.6.3 The Alt D key (display inhibit). This key toggles the 'Display Inhibit' mode. Use it to inhibit direct writing to the screen when PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 26 running under a multi-tasking operating system such as Doubledos. It has been tested and works under Doubledos Version 4.0. 3.6.4 The Alt P key (printer toggle). This key toggles the printer on and off. When the printer is turned on, any incoming data will be printed in real time. If you intend to print files received at 1200 bauds in the packet communications mode, use a print spooler or you may loose data. The printer is automatically turned off in the packet mode when a disconnect occurs. 3.6.5 The Alt F key (Digipeat monitor toggle) This key toggles the digipeat display function on and off. If the Digipeat Display Function is active, any signals digipeated through you will be stored to the PK232COM.RUN file and a 'beep' will be sounded for each packet being digipeated. The status display window will also show a [D] at that time. The MDIGI function is set 'ON' when the Digipeat display function is 'ON', this means that digipeats will show up while you are connected to someone. The default state for the Digipeat Dis- play Function is OFF. 3.6.6 The Alt R key (Message Relay toggle) This key toggles the Store and forward Message Relay Capability of your system on and off. If the Message Relay Capability is active (toggled on), any one who connects can store a message in your system using the ':QSP: <callsign>' NC/L function. If the Message Relay Capability is not active (IE. toggled off) anyone who attempts to ':QSP: a message' will receive a ':QNO: 1' "error" message. The status display window will show a [R] when the Message Relay Capability is active. The default state for the Message Relay Capability is loaded from the PK232COM.SYS file. When the Store and forward capability is active, the suffix 'R' will be added to the '*** PK232COM 1.40' message received by anyone connecting to your system to notify them that they can store messages. In this manner they don't have to try and get ':QNO: 1' error messages when the feature is toggled off. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 27 4.0 PK232COM disk files The following disk files are associated with the program. 4.1 PK232COM.COM This is the program. You activate it from DOS by typing the word PK232COM followed by ENTER in the normal manner of invoking DOS commands. 4.2 PK232COM.RUN This is the file containing the captured incoming text. This file contains incoming data from the PK-232 recorded while the 'capture to disk' function was active. 4.3 PK232COM.SYS This file contains the configuration information for both the program and the PK-232. YOU MUST EDIT IT before you run the program on the air the first time. Use your word processor in the NON-Document mode. You only need to run this function when you first power up the PK232 if you have installed the batteries or if you have run YAPP or a similar program since the last time you ran PK232COM. The contents of the file are as follows. 4.3.1 The first line. The first line contains your callsign. Please do not use G8BTB. Replace G8BTB with yours. You may use / characters if you wish. This is the call sign that will be used in the non- Packet modes. You may thus use "portable designators" such as G3ZCZ/A, G3ZCZ/W3 or G3ZCZ/4X, which you cannot do in Packet. IF YOU DON'T CHANGE THE CALL SIGN, YOU WILL GET AN ERROR MESSAGE AND THE PROGRAM WILL NOT RUN. This is the call that will be monitored for in the Digipeat monitoring mode. In this mode which is toggled on and off by the Alt F key, if someone uses you as a digipeater while you are not connected to anyone else, the event will be logged to disk. This mode will only work if your callsign as stored in this line is a valid (uppercase only) packet callsign. For example, if the callsign is G3ZCZ then the sequence >G3ZCZ> will be recognised as a digipeat and the event logged. Thus for example 4X6AA*>G3ZCZ>4Z4ZB would be logged as a digipeat event. Now if the callsign in this line is G3ZCZ/4X then the event will not be recognised as a digireat PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 28 because the computer would be checking for a >G3ZCZ/4X> sequence or in this example 4X6AA*>G3ZCZ/4X>4Z4ZB which it would never see. This option is inhibited for reciprocal callsign operators due to the AX2.5 protocol itself. If you have a / character in your callsign, and use the base call for packet identifying the location in the CQ text, then the function will work if you place the "portable location" as a suffix. For example, if the call is G3ZCZ/4X and the packet identification is G3ZCZ, then the digipeat monitor will work. If the call was entered as 4X/G3ZCZ the digipeat monitor would check for the sequence >4X> and would not appear to work. Store your callsign using uppercase characters if you want this option to work (IE. G3ZCZ). If you use lower case (ie. g3zcz), the option will not be enabled as recognition will never take place. The PK232 automatically converts case to upper case in the non packet communications modes. 4.3.2 The second line. The second line contains the AMTOR SELCAL configured for your callsign. You use it again later to tell the PK232 what the SELCAL is. This line just tells it to PK232COM. 4.3.3 The third line. The third line contains the line of text transmitted by the PK-232 in a CQ call (in any mode except for MORSE). Think of this message as a CQTEXT line. Edit this line as well. 4.3.4 The fourth and fifth lines The band and power information are set up from the default values stored in the configuration file PK232COM.SYS. They are displayed in the status window. If you operate on another band or your transmitter uses a different power level change the default values in the file to reflect your custom default state. The fourth line contains the band information. The default value is 2 for 2 Meters. Use the Meter value for the band to keep the display correct. The fifth line contains the value for the transmitter power. The default value is 10 for 10 watts. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 29 4.3.5 The sixth line The sixth line contains a number which tells the program how long to wait before transmitting a CQ call when in the beacon (automatic) mode. A value of 4 corresponds to about 2 minutes. This value of time will vary depending on the clock speed of your computer. You may have to experiment with different values. The default value is 0 which inhibits the beacon mode. 4.3.6 The seventh Line The seventh line configures the LAN store and forward capacity of the system also known as the Message Relay Capability. If it is a '0' (default state) your computer will not accept messages for forwarding. If it is a '1', it will. See Appen- dix 2 for details about LANs. Remember, if you configure your computer to store and forward messages, you have a moral obligation to deliver them. The status of this function shows up as an [R] in your status display and in the connect message transmitted to the other station at connect time, as an 'R' suffix to the message when active. 4.3.7 The eighth line This line contains the default Communications port. The default value is 1. You must leave it set to 1. THIS VERSION OF PK232COM CAN ONLY BE USED WITH COMM1. 4.3.8 The ninth line (TNC type) This line tells the program which TNC you are using. The PK232 command set is slightly dif- ferent to those of TNC2 in the packet mode. Thus the command dialog has to be changed somewhat to make the 'SOLO, TRAFFIC, CQ/BEACON and MAIL' ter- minal modes work correctly for different TNC's. NOTE that program does not check the TNC in the Non Packet modes, so for example if you try to set a TNC2 to AMTOR, PK232COM will send the PK232 commands to the TNC2 which should then return an error message. Valid TNC's are PK232 TNC2 (MFJ 1274). 4.3.9 The remaining lines The remaining lines contain commands to the PK- 232. For further information about them refer to the TNC manual. The example in the PK232COM.SYS file is as follows. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 30 BEACON EVERY 0 CBELL off CONSTAMP ON CHCALL ON CHDOUBLE ON CMSG ON CTEXT SHALOM you have connected with G3ZCZ/4X daystamp on eas on echo off flow off mycall G3ZCZ MYALIAS G8BTB MYSEL GZCZ newmode on NUCR ON nulf on UNPROTO CQ users 1 usos on If you use a different TNC (other than the PK232) you may have to edit this command list. 4.4 PK232COM.LOG This file contains the log entries. It will be created automatically to intialize the logging function. The format of the logbook file is the same as that created by the G3ZCZ CONTEST.BAS program and both files are designed to be appended into the G3ZCZ LOGBOOK DATABASE package presented as part of the PC-HAM software package. It should be edited with a word processor in the non document mode to delete the first line and clean it up before the file is appended to the DBASE logging package data files. 4.5 PK232COM.DIR This is a directory file. You use it to store connect paths or name/callsign relationships. Examples are Joe G3ZCZ Alon 4Z4ZB V 4X6AA Milt 4X6AA LR 4X6LR hf-il 4x4hf v 4z4zb 4x4il hf-rj 4x4hf v 4z4zb 4z4rj You create this file with your wordprocessor in its non document mode. You must leave AT LEAST one space character between the key word and the connect path. When you type in the key word, the program does not care about upper or lower case. If the program does not find the key word, it will try to connect with whatever you typed in. If you already have a YAPP.DIR file just rename it to PK232COM.DIR. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 31 4.6 CONFIG.SYS You must have a CONFIG.SYS file on the boot disk if you are going to use the disk logging features. This file must contain the line FILES = 20 See the DOS manual for more information about the CONFIG.SYS file. 4.7 *.MBX These are the files associated with the stations you have designated as store and forward mailboxes. Thus if for example you want to use 4Z4ZB as a store and forward mailbox, you will create a file called 4Z4ZB.MBX using the non-document mode of your word processor. In this file you will put a list of the call signs of the stations 4Z4ZB can connect to reliably. If for example you want 4Z4ZB to be able to store messages from you to 4X6AA, 4X6LR, G3ZCZ, ON8IK, F0WN,and G8BTB, you would put those call signs in the file, one call on a line as follows. 4X6AA 4X6LR G3ZCZ ON8IK F0WN G8BTB When the QRU function is invoked either by you using Control Function key 3 or by 4Z4ZB connecting to you and sending you the command :QRU: , any messages addressed to any of those stations (EG. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as you tried to QSP the messages manually or G3ZCZ or ON8IK connected to you. The file names will be changed to *.OLD. You must create one file for each designated store and forward station, ie. 4Z4ZB.MBX, G3ZCZ.MBX etc. 5.0 Initialization 5.1 Copy the files to a working disk. 5.2 Edit PK232COM.SYS. If you are upgrading from a previous version of PK232COM, note that the new .SYS file may not compatible with the old one. 5.3 Copy the new PK232COM.SYS onto the old one. 5.4 Put the working disk into the active drive (the one with the > prompt). 5.5 Make sure that the file CONFIG.SYS exists and contains the statement FILES=20. 6.0 Running the Program 6.1 Make sure that the PK-232 is connected to the computer. 6.2 Make sure that the DOS calendar date and time are set to UTC. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 32 6.3 Run the program by typing the word PK232COM followed by the ENTER key. 6.4 When the program begins, you will default to PACKET mode on VHF (Just like the PK-232 at switch on) in the TRAFFIC terminal mode. If the PK-232 is not set to the correct baud rate and parity type the * characters as explained in the PK-232 manual. 6.5 Initialize the PK232 using the relevant function key (ALT F2). If at this time or at any other time, you see 'PK232 NOT RESPONDING' displayed in the status window, you have a problem in the communications between the PK232 and the computer. 6.5 At this time, the computer will load the date and time into the PK-232. You may thus power down the PK-232 when it is not in use. If you have not put a battery in the TNC, reconfigure the defaults using the ALT F2 key. 7.0 Mailbox features 7.1 Answering Machine. The program includes an AMTOR and PACKET mode "answering machine" facility. You can leave messages on your disk (in the same directory as the PK232COM.* files, if you are using a hard disk), for different stations. When someone connects to you, if you left a message for him, he (or she or even it as the case may be) and only that station will receive it automatically. 7.2 Mail Beacon (Annunciator). To ensure that people know that you have left a message for them a 'MAIL for' list is loaded into your Packet Beacon and transmitted every 30 minutes (Refer to the BTEXT command in the TNC manual) as ':QTC:' followed by a list of calls. If no mail is pending then beacon transmissions are inhibited. This conforms to good operating practice on crowded channels (at least inhibiting the beacon does). The mail beacon in the AMTOR mode is transmitted as part of the beacon autocq message. It is automatically updated when a message is transmitted. If you don't set the beacon (see below) you will not transmit a mail beacon text in your AMTOR CQ message. The Mail beacon text is set up either when you tell the computer to set it up using Shift function key 6 or when you disconnect a packet QSO from another station. In this manner you may update the list while the program is running, for example by using Sidekick to write a message, or preferably the NOTE function, and then with a stroke of Shift function key 6, you will update the mail announcement on your beacon. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 33 7.3 How to leave a message You can use the note function (Control function key 3) or type the message as a document file on Wordstar, or if you use another word processor, you must leave the message as an ASCII text file. You may also use the NOTE function built into the program. If you do, the message will be given a header as if it came in from someone else. if you use a word processor to write the message, you will have to write in a header or show somehow that the message is not 'live'. You just name the message file as the callsign of the station to whom you wish the message to be sent at connect time. You must also give it the filetype of 'OUT'. For example a message for G3ZCZ would be stored on the disk as a file named 'G3ZCZ.OUT', and similarly a message to 4X6AA would be stored on disk as '4X6AA.OUT'. Once the message has been sent, an entry to that effect will be made in the PK232COM.RUN data capture file. The message file will then be renamed and given the file extension '.OLD'. At that time any previously existing mail file with the file extension '.OLD' will be deleted. This stops the addressee receiving the message on successive connects if you can't delete it for some reason (you forget) while at the same time, the message is still available to you in case you need it. You should use a utility program if you want the calls in the mail beacon sorted. You may for example wish to sort them alphanumerically or in the order of the date that they were left in your answering machine. 7.4 Remote File Downloading (Packet Mode Only). There comes a time when you want to leave a file on your system for someone to download later. You can do this by using NC/L to control the transfer. You must leave the file in a subdirectory called \PK232COM\FILES. You must first create it if it does not exist. The station who wants the message just asks for it using :QBM: <filename>, note they do not need to use the full subdirectory path. For example, you have the latest ARRL DX bulletin, and you want to pass it on. You could pass it to selected people by copying the file to individual messages with the filetype '.OUT', eg. 4X6AA.OUT, 4Z4ZB.OUT or even G3ZCZ.OUT if you want me to get it, which wastes a lot of disk space. On the other hand you could tell people that the file was available for downloading, either in the CTEXT connect message line which everyone gets when connecting to you, or in individual ('.OUT') messages. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 34 If you include the following in your CTEXT message "ARRLDX.015 now available" people will know that to download it, they just have to type the line ':QBM: ARRLDX.015' (one space character between :QBM: and the file name) to get the file. This program is not designed as a BBS, however if you copy the contents of the \PK232COM\FILES subdirectory into a file called DIR (USE DIR > DIR in DOS), anyone can get a list of files the files you have stored in it for downloading by typeing :QBM: DIR. Since they do not get the real directory, just what was in it at the time you copied it into the file 'DIR', you may keep "hidden" files in this subdirectory. You may thus leave a file for someone to download, tell them by leaving them a message (which they will get automatically when they connect) and no one else connecting will know that it is there. When the QRU function is invoked either by you using Control Function key 3 or by 4Z4ZB connecting to you and sending you the command :QRU:, any messages addresses to any of those stations (EG. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as you tried to QSP the messages manually or G3ZCZ or ON8IK connected to you. The file names will be changed from *.OUT to *.OLD. You may only use the QRU function with stations designated as Store and Forward mailboxes. Put a list of stations that you can connect to reliably in your <callsign>.MBX file and send it to other stations in your LAN also using PK232COM Rev 1.36 or higher. They will then be able to dump their mail messages on you and you on them. If they do the same and send you their file, then you will be able to send messages via them for stations that they can work. While QRU gives you the capability to bulk upload messages to another station in your local area, when you take your machine off line, it may also be used to transfer messages between two LANs (such as the Baltimore and Washington DC Areas) via well sighted gateway digipeaters. 7.5 Remote Beacon shutdown. I recognize that some stations may abuse the beacon facility of this program. I have thus built into the program a 'remote shutdown' capability. If someone running PK232COM has their beacon timer set too often, connect to them in the Packet Communications mode only at present, and tell them to :QRT: which will clear their beacon mode and take them off the air for a while at least. APPENDIX 0. UPDATES/REVISION HISTORY 1.30 PACKET MODE Automatic Logging of Connects. Automatic CQ beacon added. AMTOR Time shown in 'OVER' sequence. Callsign sequence text added in ARQ call. Automatic CQ beacon added with logging in beacon mode. NON PACKET MODES Semi PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 35 automatic logging added. Call sequence changed to one line except for CQ calls. Retry sequence works in all modes. 1.31 Contest Mode. Function key 3 operation slightly modified. AMTOR answering machine added. Overwrite of status window fixed. 1.32 Packet Mode Store and forward LAN :QSP: capability added. 1.33 :QBM: message/file downloading added in Packet Mode. Digipeat traffic mode logging added. File handle bug. 1.34 File handle bug fixed, logging/capture file opens/closes with each QSO. Digipeat detect works for reciprocal operators, ie >G3ZCZ> for G3ZCZ/4X. Logbook file created if non existant. Some changes in AMTOR beacon signal recog- nition algorithm. PK232COM.DIR directory added. 1.35 Digipeat detect now stores data as well as address information on disk. 1.36 LAN :QRU: store and forward added, code condensed. Display of Multiple connect mode added. Changes in NC/L :QBM: changed to :QRV: in message mode only. Digipeat logging does not indicate times of logging on/off. 1.37 AMTOR now doesn't send Brag Tape in non beacon automatic CQ mode. Timeout added in PACKET Beacon mode to stop station connecting and holding system. 1.38 V and H (direct Packet mode VHF/HF) added to function key 6. Code condensed again. AMTOR ROBOT override manual mode added. Packet loop back call added. 1.39 CQ text change added to Alt F6. AMTOR non beacon mode auto CQ sends a callsign sequence and +? when someone calls in. Note feature added to Cont F3. QRU echo's QSP to sending terminal. Printer toggle added. RTTY 'RY' changed back to single line in CQ mode. AMTOR CQ works with EPROM version 4/87. Digipeat Display function now toggled on/off by Alt F key (default is OFF). CQ delay time now adjustable on-line. Minor code changes within the program. 1.40 Thirdpary callsign correct in 'QNO 1' response situation. Alt R key (Message Relay Capability toggle) added. TNC type line added to PK232COM.SYS. TNC2 code added. Additional Baud rates added. Internal code condensed. An active Store and forward Relay status is indicated in connect message '*** PK232COM 1.40' by the 'R' suffix. SIGNAL mode [G] added to function 6. Digipeat display function also now controls 'MDIGI'. 1.41 Packet mode Baudrate, shift reverses (change in 1.40) now done in command mode. Delay added in Alternate function key 2 (TNC Initialise routine). Commands transmitted in command PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 36 window, replies now show up in INwindow. APPENDIX 1. ANOMALIES (and BUGS) Since the Program right now has no way to check the command/converse mode status of the TNC, you may see various cmd: and error messages from the TNC when using the function key commands. Ignore them for now. If you get an error message, try using the function key again. In the AMTOR Beacon CQ mode, if the other station drops the link while you are recording the text, the program will time out before logging the QSO and restarting the CQ sequence. If someone else calls in before the timeout has occurred, the text from both stations should be captured to disk, but the log entry may not show both stations, thus the 'LOG' must be compared with the 'RUN' file for QSL purposes. In the AMTOR Beacon CQ mode, if another stations sends a +? in the FEC mode, the beacon will attempt to send the PK232COM.TXT file. The PK232 however is not in the converse mode at that time and will interpret the text of the file as commands. If by some chance, the text corresponds to a valid command the PK232 will execute it and you may not notice that it did until you begin to wonder why nobody is replying to the beacon. As such I recommend that the first character of each line in the file PK232COM.TXT be a non valid command character such as a number or a period (.) or an other punctuation sign. PK232COM versions 1.00 to 1.39 were written for a PK232 with an Oct 1986 ROM. There may be differences with later ROMs. Version 1.39 works with the April 1987 ROM. APPENDIX 2. Local Area Network Capablity VHF Packet radio systems can be considered as part of a Local Area Network (LAN) in which messages can be left by one station in the computer belonging to a second station. At HF the same is true, but the area becomes greater. The basic problem here is that people can only send and receive messages to or from you when you are on-line. To compensate for this, BBS stations were developed which allowed both messages and bulletins to be stored by anyone for later retrieval. PK232COM allows you to store messages in your computer so as to use it as an automatic answering machine. Thus by storing the messages in a file called by the name of callsign, with the file extension '.OUT', anyone connecting to the computer will get their message without having to request it. PK232COM Version 1.32 extends that concept to cover the eventuality of you wanting to take your computer off-line for some reason. You may now load the message into any other computer you can connect to using elements of the Q code adapted to the High Level Network Com- munications Language (NC/L) proposed in my book Software for PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 37 Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 USA. The protocol is as follows. When connected to someone who has their computer configured as a host, if you want to store a message you send the following instruction to the other station :QSP: <callsign> where <callsign> is the call of the station that the message is for, not the callsign of the host station in whose computer you are storing the message. [Note use only one space character after the :QSP: ]. PK232COM sends the :QSP: message automatically using Control Function Key 3. For example if you want to store a message for 4Z4ZB in 4X6AA's computer which is configured as a Store and Forward system, you would first connect to 4X6AA and then send the message as :QSP: 4Z4ZB . The other computer will respond either with a statement saying that it is ready for you to go ahead, or send a message saying that it can't comply. If it is ready you get a positive reply which will take the form :QRV: <callsign> which if you know the Q code, means " I am ready to accept a message for <callsign>". At this time you may go ahead and send the message. If you type the message at the keyboard, you may use either a control Z (^Z) character or the character sequence :EOF: followed by a carriage return (the ENTER key) to terminate the message. If you have first written the message into a text file you may then send it using function key 2 and the termination sequence is automatic. Once you have completed the message, the other (host) computer will either reply that the message has been successfully stored or give you an error message. If the message is stored and ready to be sent next time the addressee connects to that computer, you will see the message :QSL: on your screen. If something went wrong, you will get back a negative message taking the form :QNO: followed by a number. The number tells you why the operation failed. Message Format The message is stored just as if you had left it in your system (except that a header is added identifying the time of reception and the call of the sending station). It will contain a header showing the date and time it was received and your callsign. Should a message for that station already be in the system, yours will be appended to it. In the event the your upload is aborted, the amount of text received before the abort occurred will be stored as the message. When you disconnect from the host station, its mail beacon will be updated. Once the message is loaded in the host, it can only be deleted by PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 38 the operator of the host station. When the addressee connects to the host and receives the message, the file type will change from '.OUT' to '.OLD'. File downloading See section 7.4 for the use of :QBM: for downloading text or ASCII files from another PK232COM system. APPENDIX 3 BASIC NC/L DICTIONARY Messages can be transferred into any other computer you can connect to using elements of the Q code adapted to the High Level Network Communications Language (NC/L) proposed in my book Software for Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 USA. To receive a message, do nothing, you will receive your mail automatically when connecting/linking to a PK232COM station. You cannot read messages adressed to another person. :QSP: To leave a message, send :QSP: callsign the callsign is that of the station you wish to leave a message for. :QRU: To upload messages from one PK232COM (1.38+) system to your computer send :QRU: :QBM: To download a message, send :QBM: filename.type The filename.type is the file you want. For example :QBM: dir :QBM: help :QBM: pk232com.doc :QRT: To shut down a packet mode beacon station who is causing QRM, connect to the station and send :QRT: Computer responses :QSL: callsign Confirms receipt of message to that callsign. :QRV: callsign The computer is ready you to send the message. End the message with a control Z (^Z) character, or the sequence :EOF: . :QNO: 'NO' or error QNO Error Values. The following error numbers are associated with message store and forward operations. PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 39 1 Computer not configured as Store and Forward system. 2 Requested ASCII file/ message (:QBM:) does not exist. 3 You made an error in the name of the callsign for whom the message is intended (It must be at least 3 characters long). 4 File creation error in host system. 5 Error occurred during reception and storage of message. Could be that the computer ran out of space on the disk, or something else went wrong in storing the message. 6 :QRU: You are not authorised as a store and forward mailbox. 7 :QRU: Error in opening <callsign>.MBX file. 8 :QRU: Error in closing <callsign>.MBX file. 9 :QRU: Sequence Error in callsign of message to go. The bad callsign will be shown after the error number. :QTC: messsage list. This is not quite a response, but it precedes a list of callsigns for whom messages are stored up on a computer. It is used in Packet Beacon transmissions or AMTOR Beacon mode CQ calls. PROPOSED EXTENSIONS :QYU: YAPP format file upload. :QYD: YAPP format file download. APPENDIX 4. USING OTHER TNC'S. PK232COM is designed for the PK232. However the PACKET mode capabilities can be used on other TNC's. There are minor differences in the command dialog between different TNC's. The dialog differences affecting the operation of PK232COM are built into the program and set when the TNC type is read from the PK232COM.SYS file at the program load time. The non packet modes will obviously result in error messages if attempted on a packet mode TNC. The following notes apply to different TNC's or digital communications controllers. 4.1 TNC2 (MFJ 1274) 4.1.1 Default Commands. Edit the PK232COM.SYS file taking out the PK232 specific commands, namely anything that is not mentioned in your manual. Add in the default state for the TNC commands not included in the file and make sure that you set AUTOLF ON and MCOM ON 4.1.2 Program differences. The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. Software controlled HF/VHF switching. Software controlled baudrate switching. MAIL Packet terminal mode (Alternate Function key 4). PK232COM.DOC (c) G3ZCZ 1987 PK232COM VERSION 1.41 PAGE 40 CQ/BEACON Packet terminal mode (Alternate Function key 4). TNC Transmit Buffer flush (Control Function key 9). Digipeat display and logging function (Alternate F key). APPENDIX 5. NOTES I'm always interested in your bug reports, comments and suggestions for changes. PK232COM.DOC (c) G3ZCZ 1987